Improve test helper efficiency: crypto/rand and exponential backoff #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Test helpers had two inefficiencies: predictable random number generation using PIDs, and fixed 30-second polling intervals for cluster readiness checks.
Changes
randInt()intest/helpers/config.go: Replace PID-based pseudo-random withcrypto/randfor proper uniqueness in resource namesWaitForClusterReady()intest/helpers/validation.go: Replace fixed 30s sleep with exponential backoff (10s → 60s cap, 2x factor)test/go.mod: Add module description commentBefore/After
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.